caching proxy造句

• caching proxies are proxies that cache server responses
  代理是缓存服务器响应的代理。
• The caching proxy is an extension to the servlet caching
  高速缓存代理是servlet高速缓存的扩展。
• Within the network, optionally caching proxies can be installed
  在网络中，可以选择安装缓存代理。
• A caching proxy that receives a request searches for matching responses that might already exist in its cache
  接收请求的缓存代理将在其缓存中搜索可能已经存在的匹配响应。
• On subsequent requests, caching proxies send matching responses back to clients directly out of their cache
  对于后续的请求，缓存代理会直接从其缓存中将匹配的响应发送回客户机。
• The caching proxy provides a caching solution, but is typically placed in front of the web servers and closer to the end users
  高速缓存代理提供了一个高速缓存解决方案，但是通常位于web服务器的前面（距终端用户更近）。
• Collocation is also supported for content based routing, but only when using bind-specific web servers and a bind-specific caching proxy
  并置还支持基于内容的路由，但是只有当使用特定于绑定的web服务和一个特定于绑定的高速缓存代理时才支持。
• In addition to the servlet caching, this caching solution can be further extended by using the caching proxy part of the edge component
  除servlet高速缓存外，这个高速缓存解决方案能够通过使用高速缓存代理（edge组件的一部分）进行进一步的扩展。
• By using caching proxies, each page would be delivered from the portal only once and then reside within the cache until the content becomes invalid
  通过使用缓存代理，每个页面都只需从门户交付一次，然后此页面将驻留在缓存中（直到内容无效时为止）。
• Subsequent requests to the same page within the lifetime of the content are responded to directly by the caching proxy, and thus do not generate load on the portal server
  在内容的生存期内，对同一页面的后续请求都将由缓存代理直接响应，因而不会在门户服务器上生成工作负载。
• With the new adaptive page caching, portlet caching, and object caching functions, ibm websphere portal v5.1 can efficiently serve the dynamic parts of a web site while projecting the static parts into caching proxies or browser caches
  通过利用新的自适应页面缓存、portlet缓存和对象缓存功能，ibmwebsphereportalv5.1可以高效地服务于网站的动态部分，同时将静态部分放入缓存代理或浏览器缓存中。
• It does not need to be configured in the browser or the network explicitly . the reverse proxy behaves exactly like the caching proxy, in that it searches for a matching response in its cache and forwards the request only if no matching response is already available
  它并不需要在浏览器或网络中显式进行配置，反向代理的行为与缓存代理完全一样，它在其自身的缓存中搜索匹配响应，只有在没有可用的响应时才转发请求。